-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Propose that we move OTEPs into the specification repository. #266
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I support this idea, but would remove the text/
part of the directory path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I appreciate the effort to reduce overhead, I just added a few questions about details.
Just a note from the spec meeting today; We should ensure that when this move happens that we clarify the use of normative language in OTEPs (and where needed, ensure that existing OTEPs are normalized to that decision) |
@jsuereth do you have a plan / schedule in mind for merging and executing this plan? |
We will merge this OTEP as it has enough approvals and will start the work, tuning further details, such as:
|
No description provided.